IMPORTANT- This is a public beta of Unreal Mac. While we hope it fixes many bugs, it has not been through the normal full testing procedures so there may be problems with it. It is likely some new problems may have been introduced from previous versions. If bugs from previous versions still exist, report them to unrealbeta@westlakeinteractive.com. Westlake can not provide tech support for Unreal, so please send only bug reports, not requests for help setting the game up. PLEASE DO NOT SEND BUG REPORTS TO OTHER WESTLAKE EMAIL ADDRESSES!
Contents
A) Installation Instructions
B) Troubleshooting
C) Notes on 220 and 224
D) 220 Beta 3 Fixes & Improvements
E) Rave Advanced Options
F) Copyright notices
A) Installation Instructions
Important: The 220 Beta 3 application included in this update will only work if you have version of 220 Beta 2 installed. If you have an older version of Unreal (1.0.x) you must update to 220 Beta 2 first, and then install this patch.
1) Run the Unreal 220 Beta 3 updater and select your Unreal 2.2.0B2 application.
B) Troubleshooting
3Dfx screens are too dark - The LightModify variable in previous versions of Unreal was accidently removed from 220. It is now active again. To turn this feature on, go to Advanced Options, select the Rendering section, and click on "3Dfx Glide Support". Edit the "LightModify" field and set it to "0.5". This will make the game 50% brighter overall. You will have to quit and re-run Unreal to make the change take affect. Setting the value to "0.0" will return to normal lighting, "1.0" to twice as bright, etc.
Bots always run at skill level 255- Due to a bug in the PC script code, the bots are stuck at level 255. To fix, after loading a bot level, in the console type Set bots skill=0 (or 1 or 2 or 3.)
Unfortunately you have to do this each time a bot map loads. One fast way to execute the fix is to bind the "set bot skill x" to a key so you can hit that key at the beginning of a level.
Save games from 219 or earlier versions don't work right - The notes in the original 220 patch were incorrect, previous save games do not always work in 220. This is due to engine changes from the PC, and is similar to the behavior of Unreal PC 220. Some save games may load fine, others will give errors. If your save games don't work, you can jump to a specific level by double clicking its corresponding map file in the "Maps" folder. Check the original Unreal Mac 1.0 Read Me for cheats to give yourself back your weapons and other items.
Crashes or out of memory errors - If you get crashes when switching levels or out of memory errors, set the Minimum size for the Unreal application to the same as the Preferred size. To do this, select the Unreal application icon in the Finder and select "Get Info" from the File menu. If the window that comes up does not have Minimum and Preferred Size boxes, select "Memory" from the "Show:" popup menu. Edit the values for Minimum and Preferred and close the Get Info window. A value of at least 95,000K is best for running Unreal.
RAVE out of texture memory errors - Make sure MipMapping is turned off under RAVE Advanced Options. Turning on Vertex Lighting and turning off Volumetric Lighting may also help. This may also be a problem with the ATI drivers, so check for new updates on ATI's web site (www.atitech.com).
C) Notes on 220 and 224
With the 220 releases, Unreal Mac is on parity with the current PC version of Unreal. We apologize for the delay in releasing the Mac version of 220, many factors both in and out of our control caused it to take much longer than we planned. A new PC release, 224, is scheduled to come out some time in the next month or so, and we have already begun working on early versions of the 224 code on the Mac. The Mac version of 224 should be available much closer to the PC release than previous Mac patches.
To find Internet games to join in Unreal, you should download the latest copy of UnrealFinder from http://quakefinder.telefragged.com/news/ UnrealFinder is not supported by MacSoft or Westlake Interactive, but is a great shareware utility for finding Unreal games.
D) 220 Beta 3 Improvements
Beta 3 Fixes
* Many crashes when hosting net games, switching levels in net games, and starting Bot matches have been fixed. For the technical minded wondering what this bug was, it turns out to be a memory overwriting bug that was in the original PC 220 script code. Longer map names and player names would tend to make the crashes happen more often, since more memory was overwritten. Why does the PC not exhibit the bug? Its unknown, but probably just a lucky quirk of the way memory is allocated or padded under Windows. Epic knows about this bug and has fixed it for future releases on both PC (and thus the Mac).
* Speech synthesis works again (it was broken in earlier Mac 220's).
* The "LightModify" parameter in 3Dfx mode works again. To turn this feature on, go to Advanced Options, select the Rendering section, and click on "3Dfx Glide Support". Edit the "LightModify" field and set it to "0.5". This will make the game 50% brighter overall. You will have to quit and re-run Unreal to make the change take affect. Setting the value to "0.0" will return to normal lighting, "1.0" to twice as bright, etc.
Original 220 Fixes
Mac Specific
* Crashes in RAVE with high detail textures (especially on Dcrater.unr) fixed.
* Too dark screen flashes in RAVE when underwater or being shot fixed.
Multiplayer Improvements
* Player movements are now compressed with a predictor-corrector scheme,
allowing for smoother movement of enemies.
* New multiplayer game styles, including Classic, Hardcore, and Turbo,
can be selected from the game options menu.
* Fixed player and spectator counts.
* Fixed becoming ghost when killed while starting to feign death.
* Spectators can now see the scoreboard.
* Spectators can cycle through other player views by pressing fire, and
return to their own view using the alt-fire button.
* Spectators can go through portals.
* Fixed support for multiple skin .int files (now can add user skins in
new utx files without breaking compatibility).
* Improved team scoreboard.
* Skin and mesh selection always remembered.
* Spectators not shown in the scoreboard.
* Skaarj player swimming and dodge roll animations played correctly.
* In team games, players properly start at appropriate playerstarts in
levels where playerstarts are marked for specific teams.
* Fixed King of the Hill gameplay bugs.
* Fixed jumpboot respawning problem.
*
Internet Play
* Improved bandwidth usage for temporary effects like projectiles.
* Player movements are now compressed with a predictor-corrector scheme,
allowing for smoother movement of enemies.
* Movers are simulated client-side, and players based on movers have
their location updated by the server relative to the mover position.
This allows smooth mover movement prediction on the client.
* Optional game password can be set to limit access to a server. Clients
can enter the administrator or game password from the player selection
menu.
* Fixed "little chess piece" cheat and some other security holes..
Server
* Fixed remote administration (see Server Tips for information).
* Remote administrators can finally execute console commands on the
server.
* The "AllowAdmin" setting is no longer used. To make your server
remotely manageable, just set the "AdminPassword" in "Advanced Options
/ Game Settings".
Rendering
* "TIMEDEMO 1" command provides frames-per-second statistics at any time.
If started during the flyby sequence, it provides statistics for
exactly one loop of the flyby, for comparison to other systems.
"TIMEDEMO 0" turns it off. Thanks to Jack "Mek" Porter for integrating
the code.
Player Controls
* bFreelook
* FOV snaps back to modified value.
* Optional mouse smoothing.
* GetWeapon console command can be used to bind any key to a specific
weapon.
* Added weapon flash effects, and option to turn them off.
* Fixed centerview problem.
Single Player
* Fixed problem where splashes didn't play on some levels.
* Fixed problem where a healing zone reduced your health to 100 if it was
above 100.
* Fixed problem where pickups like the shieldbelt were de-activated after
a level change.
* Improved the "Advanced Options" screen.
* Fixed problem with scuba gear interfering with armor.
* Crucified nali is solid.
BotMatch
* Bots have greatly improved understanding of how to use lifts, and how
to use triggered doors and lifts.
* Bots never get frozen after dying.
* Fixed bug where bots would disappear from the game.
* Bots have a better understanding of how to do the ASMD combo move and
other weapon special moves.
* Improved navigation code for swimming, jumping up onto ledges.
Coop games
* Listen server player weapons travel from level to level.
* Fixed weird movement problem in open areas on fast machines during coop
play.
* Translocator works properly in coop play, and everyone gets one.
Separation of player and system configuration
* The new User.ini now contains all user-specific Unreal settings such as
the keyboard and mouse configuration.
* Unreal.ini only contains system-wide options.
* Default.ini contains default values for everything in both User.ini and
Unreal.ini.
* If you're going to a LAN party and want to bring your configuration
with you, just bring User.ini.
Heads Up Display
* The HUD is now responsible for drawing its owner's weapon. A local
player's HUD RenderOverlays() function is called every tick. It calls
the RenderOverlays() function for its owner's weapon (and potentially
other actors). RenderOverlays() is called before the view flash and
fog is applied, unlike PostRender(). As a result, InvCalcView() was no
longer needed and was removed from Inventory.
Messages
* ClientMessage has been rewritten to take an optional message type and
optional message beep boolean. The message type can be used to
determine how the message is displayed on the screen. See
Engine.Console.PostRender for information.
* Engine.Console.PostRender has been moved from C++ to UnrealScript.
* The console now asks the gameinfo object to handle messages before it
displays them. A GameInfo class can employ DisplayMessages(Canvas C)
to paint messages instead of the default Console.
* There are now weapon based death messages. Weapon deathmessages are
coded strings that take the form:
%k killed %v with the %w.
* %k is replaced with the killer's name.
* %o is replaced with the victim's name.
* %w is replaced with the killer's weapons name.
* The actual order of the % codes in the deathmessage is irrelevant.
E) Rave Advanced Options
Several new RAVE options have been added to the Advanced Options (and behavior of a couple has changed):
• MipMapping- normally off for pre-Rage 128 cards, this makes textures drawn far away look better.
• DisableVSync- normally on for all Rage cards, this speeds up the game by immediately drawing a frame as soon as it is ready, and not waiting for the monitor to synchronize with drawing. Turning this on may cause some flickering or tearings of shapes on the screen.
• PageFlip- uses special video hardware to display frames. This removes all flickering and tearing but is not quite as fast as when off or with DisableVSync on. Turning both PageFlip and DisableVSync on will cause one or the other to cancel out.
• Texture Composite- normally off on pre-Rage 128, this draws two textures in one pass (teture and lighting). This is faster when turned on, but causes some blocky graphics on Rage Pro cards.
• DetailBias- only useful on Rage 128 when mipmapping is on, the default is 0.0. It ranges from -1.0 to 1.0, and affects how much detail to show in mipmaps (higher numbers mean more detail, sharper graphics, slower frame rates).
• Vertex Lighting- turning this on will use a faster (but not as detailed) method of drawing lights & shadows. Texture composite and vertex lighting are mutually exclusive, so turning both on at once will have no effect.
• LightModify- This value allows you to increase the game's brightness beyond the normal settings. When it is set to 0.0, the game plays as normal. Setting it to 1.0 will make all the lighting 100% brighter. 0.5 will make it 50% brighter, etc. You must quit the game after changing this option to have it take effect.
Permission to use, copy, modify, and distribute this software, in both binary and source forms, and together with its documentation, for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of Biit not be used in advertising or publicity pertaining to distribution of this software without specific, written permission.
BIIT DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL BIIT BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
